fix: prevent ambiguous slash phrases from rendering as file links#550
Merged
Dimillian merged 1 commit intoDimillian:mainfrom Mar 13, 2026
Merged
Conversation
Contributor
|
Since you are on it, can you try fixing the bug where if a project name contains a space it doesn't render correctly on the message? |
Owner
|
@codex review |
|
Codex Review: Didn't find any major issues. 🚀 ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Synopsis
CodexMonitor was incorrectly turning natural-language slash phrases like
app/daemon,Git/Plan, andSpec/Verification/Evidenceinto file links in rendered messages.The raw
agentMessage.textfromthread/resume responsewas correct, so the issue was infrontend markdown rendering, specifically the plain-text file linkification logic in
remarkFileLinks.Before
After
Changes
docs/setup.mdlinkableValidation
npm run test -- src/features/messages/components/Markdown.test.tsxnpm run typechecknpm run tauri:dev